fix(ci): deploy beta update metadata on prerelease#399
Conversation
Previously, the deploy-update-metadata job was skipped entirely for prereleases, meaning beta channel users never received prerelease updates via auto-update. Now the job runs for all releases but only deploys beta*.yml files for prereleases, leaving latest*.yml untouched.
✅ Deploy Preview for devsydev canceled.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release workflow's metadata deployment job now conditionally overlays Electron update metadata files based on release type. Stable releases copy latest/beta Linux and cross-platform YAML files, while prereleases copy only prerelease-specific files. The prerelease publication job is made dependent on this metadata deployment completing. ChangesRelease workflow metadata deployment
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
!github.event.release.prereleasegate fromdeploy-update-metadataso it runs for all releaseslatest*.ymlandbeta*.yml; prereleases only deploybeta*.ymldeploy-update-metadataas a dependency of theprereleasejob so metadata is live before the release is publishedThis fixes the beta auto-update channel — previously, beta channel users never received prereleases via auto-update because no metadata was deployed to
dl.devsy.shduring prerelease workflows.Summary by CodeRabbit
Note: This release contains no user-facing changes. Updates are limited to internal build and release infrastructure improvements.